| blob | 8732c91573f378d7ff3cb21a5cd13fdc963e8006 |
1 # Hardware Debugging In Eclipse
3 Build a binary with debugging information using command line or via Eclipse make target.
5 Example Eclipse make target
7 
9 # GDB and OpenOCD
11 start openocd
13 Create a new debug configuration in eclipse :
14 
15 
17 you can control openocd with a telnet connection:
19 telnet localhost 4444
21 stop the board, flash the firmware, restart:
23 reset halt
24 wait_halt
25 sleep 100
26 poll
27 flash probe 0
28 flash write_image erase /home/user/git/cleanflight/obj/cleanflight_NAZE.hex 0x08000000
29 sleep 200
30 soft_reset_halt
31 wait_halt
32 poll
33 reset halt
35 A this point you can launch the debug in Eclispe.
36 
38 # GDB and J Link
40 Here are some screenshots showing Hydra's configuration of Eclipse (Kepler)
42 If you use cygwin to build the binaries then be sure to have configured your common `Source Lookup Path`, `Path Mappings` first, like this:
44 
47 Create a new `GDB Hardware Debugging` launch configuration from the `Run` menu
49 It's important to have build the executable compiled with GDB debugging information first.
50 Select the appropriate .elf file (not hex file) - In these examples the target platform is an OLIMEXINO.
52 DISABLE auto-build
54 
56 Choose the appropriate gdb executable - ideally from the same toolchain that you use to build the executable.
58 
60 Configure Startup as follows
62 Initialization commands
64 ```
65 target remote localhost:2331
66 monitor interface SWD
67 monitor speed 2000
68 monitor flash device = STM32F103RB
69 monitor flash download = 1
70 monitor flash breakpoints = 1
71 monitor endian little
72 monitor reset
73 ```
76 
78 
80 It may be useful to specify run commands too:
82 ```
83 monitor reg r13 = (0x00000000)
84 monitor reg pc = (0x00000004)
85 continue
86 ```
88 
90 If you use cygwin an additional entry should be shown on the Source tab (not present in this screenshot)
92 
94 Nothing to change from the defaults on the Common tab
96 
98 Start up the J-Link server in USB mode
100 
102 If it connects to your target device it should look like this
104 
106 From Eclipse launch the application using the Run/Debug Configurations..., Eclipse should upload the compiled file to the target device which looks like this
108 
110 When it's running the J-Link server should look like this.
112 
114 Then finally you can use Eclipse debug features to inspect variables, memory, stacktrace, set breakpoints, step over code, etc.
116 
118 If Eclipse can't find your breakpoints and they are ignored then check your path mappings (if using cygwin) or use the other debugging launcher as follows. Note the 'Select other...' at the bottom of the configuration window.
120 